home *** CD-ROM | disk | FTP | other *** search
- Path: news.ais.net!usenet
- From: support@usr.com (Jim Thomsen)
- Newsgroups: comp.dcom.modems
- Subject: Re: USR 336VI gets CRC error in win95 ppp
- Date: Sun, 03 Mar 1996 09:15:57 GMT
- Organization: American Information Systems, Inc.
- Message-ID: <313960f2.1504965@news.ais.net>
- References: <4gd22d$sbv@matahari.bae.bellcore.com>
- NNTP-Posting-Host: ts02-17.dialup.ais.net
- X-Newsreader: Forte Agent .99d/32.182
-
- On 20 Feb 1996 12:57:33 -0500, eliz@cc.bellcore.com (Elizabeth
- Gene,RRC1D209,6995790,,25975) wrote:
-
- >
- >I have an internal USR 336vi modem, and I can't connect to my ISP. I have
- >looked through the modemlog.txt and ppplog.txt logs, and I can see a
- >connection being established at 19.2 or 21.6. However, the ppplog shows
- >an error partway through the protocol, and I see 1 CRC error and around
- >10 frame errors.
- >
- >To make matters worse, the modem is now hung until I power down and back
-
-
- >Please cc to my email: eliz@bae.bellcore.com
- >
- >Thanks,
- >
- >Elizabeth
- >
-
- Elizebeth,
-
- Below is my "Top Ten" list for why CRC errors occur. Since you are
- using 95 some of the below will not apply. First off make sure the
- modem is installed to its own COM/IRQ setting. Also try lowering the
- baud rate down to 38,400.
-
- Com Overrun errors or CRC errors are usually not the fault of the
- modem. Normally they tend to be a incorrect software configuration or
- a IRQ conflict. Listed below are the most likely causes for these
- errors and some suggestions to resolve them.
-
- * Modem is not installed to itÆs own COM/IRQ. Insure the modem is on
- itÆs own unique COM & IRQ setting.
-
- * Not using a proper UART. If you are using a external modem, as our
- internals have 16550 UARTÆs built in, then make sure your computers
- port has a 16550 UART.
-
- * Not using Flow Control. We recommend using Hardware flow control.
- Set your software to Hardware flow control (RTS/CTS) and use a
- hardware flow control initialization string (AT&F1). Never use &B0 as
- it sets the port rate to variable. You want a fixed port rate.
-
- * Using a incorrect communication driver in Windows and not using
- buffering or FIFO statements in your /windows/system.ini file.
-
- If using Windows for Workgroups then ensure you are using the default
- communications driver unless the third party
- driver is needed. (comm.drv=comm.drv is the default driver)
-
- If using Windows 3.1 then try using a third party communications
- driver. Cybercom (CYBC114.ZIP) is available off our BBS and FTP site
- and is located in DL02 in either site. This communications driver has
- been tested and is the driver we recommend.
-
- Add the following statements in your /windows/system.ini file:
-
- COMxBUFFER=1024
- COMxFIFO=1
-
- (x is represents the communications port of your modem. Example - If
- your modem is on COM 2 then the statement would be, ôCOM2BUFFER=1024ö.
- The buffer size can be increased in increments of 1024 as well. These
- lines can be added to both Windows 3.1 and Windows for Workgroups. The
- COMxFIFO statement should always equal one.)
-
- * TSRÆs, large applications, and large screensavers can also cause CRC
- errors and Com Overrun errors. When downloading or uploading try to
- boot the machine with all TSRÆs turned off and all unneeded
- applications closed down. If possible try to only have the
- communications software open.
-
- * Lastly try lowering your baud rate. If you are using a 28,800 modem
- we recommend you set your port rate to 38,400 or 57,600. If using a
- 14,400 modem we recommend you set your port rate to 19,200 or 38,400.
- Again make sure you have a high speed 16550 UART if setting your baud
- rate this high.
-
-
- Regards,
-
- Jim Thomsen
- On-line Support
-
- U.S.Robotics
- The Intelligent Choice in Information Access
-
-
-